Event-driven annotation techniques

ABSTRACT

Techniques for annotating or bookmarking digital information. The digital information is annotated based upon events determined from the digital information. The digital information that is annotated may comprise one or more types of information including but not restricted to video information, audio information, images, documents, slides information, whiteboard information, notes information, and the like.

BACKGROUND OF THE INVENTION

The present invention relates to annotation techniques, and more particularly to techniques for bookmarking or annotating digital information to facilitate subsequent search and browsing of the information.

Several techniques and systems have been devised to capture digital information. For example, information may be captured during meetings, presentations, classroom lectures, demonstrations, conferences, interviews, legal proceedings, focus group meetings, surveillance activities, and the like. The captured digital information may include time-varying information such as video information and audio information, images, documents, slides, whiteboard information, notes information, and the like. Various information capture devices may be used to capture the information. The captured information is typically stored in a database for subsequent retrieval and use.

A user may want to browse or search the digital information, possibly to find sections of the information of interest to the user. However, due to the different types of information, searching and browsing the information is generally a non-trivial task. Annotations are generally added to digital information to make browsing and searching the information more efficient. For example, certain sections of the captured digital information may be marked as “important” for a meeting, or a user may want to bookmark the digital information where a specific question was asked, etc.

Some applications are available that automatically annotate digital information to facilitate search and browsing activities. However, in practice, it is seen that most of such automatic annotation techniques are erroneous and are not able to take place of human annotation. Further, the annotations are typically added (either manually or by automatic tools) subsequent to the recording session during which the digital information was captured. As a result, the annotations are not immediately available for browsing or searching or performing other operations on the information during the recording session.

In light of the above, improved annotation techniques are desired.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention provide techniques for annotating or bookmarking digital information. The digital information is annotated based upon events determined from the digital information. The digital information that is annotated may comprise one or more types of information including but not restricted to video information, audio information, images, documents, slides information, whiteboard information, notes information, and the like.

According to an embodiment of the present invention, techniques are provided for annotating digital information. A set of one or more events are identified from the digital information. Information identifying the set of events is output via an output device. User input is received indicating selection of at least one event from the set of events. The digital information is annotated based upon the at least one event.

According to an embodiment of the present invention, a time associated with the at least one event may be determined and used to annotate the digital information. In another embodiment, the digital information may be annotated for a duration of the at least one event.

According to an embodiment of the present invention, the digital information is captured during a recording session, and the operations of identifying the set of events, outputting information identifying the set of events, receiving the user input, and annotating the digital information are performed during the recording session.

According to another embodiment of the present invention, techniques are provided for annotating digital information, where a set of one or more events are determined from the digital information. A signal is received and a first event is determined for the signal from the set of events. The digital information is annotated based upon the first event. The signal may be caused due to an action performed by a user.

According to an embodiment of the present invention, a time associated with the signal is determined and an event determined from the set of events whose start time is prior to and closest to the time associated with the signal. A time associated with the first event may be determined and used to annotate the digital information.

According to an embodiment of the present invention, the digital information is captured during a recording session, and the operations of identifying the set of events, receiving the signal, determining the first event, and annotating the digital information are performed during the recording session.

The foregoing, together with other features, embodiments, and advantages of the present invention, will become more apparent when referring to the following specification, claims, and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a simplified system that may incorporate an annotation system according to an embodiment of the present invention;

FIG. 2 depicts a simplified high-level flowchart for annotating digital information according to an embodiment of the present invention;

FIG. 3 depicts another simplified system that may incorporate an annotation system according to an embodiment of the present invention;

FIG. 4 depicts a simplified high-level flowchart for annotating digital information according to an embodiment of the present invention;

FIGS. 5A and 5B depict a simplified user interface that displays events to a user and enables a user to select one or more of the displayed events according to an embodiment of the present invention; and

FIG. 6 is a simplified block diagram of a computer system that may be used to practice an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of the invention. However, it will be apparent that the invention may be practiced without these specific details.

Embodiments of the present invention provide techniques for annotating or bookmarking digital information. The digital information is annotated based upon events determined from the digital information. For example, information captured (or recorded) during a meeting may be annotated based upon a set of events determined from the captured information. The digital information may be captured during a recording session. The recording session may occur for example at a meeting, a presentation, a classroom lecture, a demonstration, a conference, an interview, a legal proceeding, a focus group meeting or activity, a surveillance activity, and so forth where information is recorded. The digital information that is annotated may comprise one or more types of information including but not restricted to video information, audio information, images, documents, slides information, whiteboard information, notes information, and the like.

FIG. 1 depicts a simplified a system 100 that may incorporate an annotation system according to an embodiment of the present invention. As depicted in FIG. 1, system 100 comprises one or more capture devices 102, a server 104, a database 106, an event detector 108, and an annotating interface 110. The various components depicted in FIG. 1 may be implemented in software, hardware, or combinations thereof. FIG. 1 is merely illustrative of an embodiment incorporating the present invention and does not limit the scope of the invention as recited in the claims. One of ordinary skill in the art would recognize other variations, modifications, and alternatives.

Capture devices 102 are configured to capture digital information. The information may be captured during a recording session. Capture devices 102 may be configured to capture or record information of different types such as audio information, video information, images, etc. Capture devices 102 may include different types of devices including, but not limited to, an audio recorder, video recorder, presentation slides recorder, whiteboard information recorder, document recorder, notes recorder, image recorder, etc. For example, for a recording session during a meeting, an audio recorder (e.g., a microphone) may be configured to capture audio information during the meeting. The captured audio information may comprise, for example, information spoken by a meeting participant. A video recorder (e.g., a video camera) may be configured to capture video information during the meeting, a slides recorder may be configured to capture slides shown during the meeting, a whiteboard information recorder (e.g., a camera configured to capture images of a whiteboard) may be configured to capture information written on a whiteboard, a document recorder may be configured to capture documents presented or distributed during the meeting, a notes recorder may be configured to capture notes taken by one or more meeting participants, and the like.

The information captured by capture devices 102 may be communicated to a server 104, as depicted in FIG. 1. Server 104 may receive the multimodal output of capture devices 102 and store the captured digital information in database 106. Database 106 may be any repository for storing digital information. The captured information may be stored in various forms. In one embodiment, as depicted in FIG. 1, the captured information may be stored as a record 112. For example, information captured during a meeting may be stored as a meeting record. Multiple records may be stored in database 106 corresponding to information captured during multiple sessions. For example, multiple meeting records may be stored comprising information captured during multiple meetings. In some embodiments, server 104 may process the captured digital information prior to storing the information in database 106. Accordingly, database 106 may store the information captured by capture devices 102 or a portion thereof.

Annotation of digital information is facilitated by events detector 108 and annotating interface 110 modules. Events detector 108 and annotating interface 110 may be used to annotate the digital information captured by capture devices 102 and stored in database 106. Events detector 108 is configured to process the digital information to be annotated and detect one or more events from the digital information. In the embodiment depicted in FIG. 1, events detector 108 may receive the digital information to be annotated from server 104 or directly from capture devices 102. Alternatively, events detector 108 may access the digital information to be annotated from database 106.

In one embodiment, server 104 is configured to stream the captured information received from capture devices 102 to events detector 108. Server 104 may stream the information to events detector 108 continuously or in a periodic manner, or upon receiving a request for the information from events detector 108. In one embodiment, server 104 may receive information captured by capture devices 102, store the information in database 106, and then communicate information to events detector 108 identifying the location where the captured information is stored in database 106. Events detector 108 may use the location information received from server 104 to access the captured information from database 106 for further processing.

Events detector 108 may detect various different events from the digital information. Events are typically detected based upon the contents of the digital information. Since the digital information may include information of various different types (e.g., audio, video, image), the event detection techniques that events detector 108 uses to detect the events may depend on the type of the information being processed. For example, various different techniques may be used to detect events from captured audio information. The events that are detected from audio information may include, but are not limited to, detecting a new source of the audio (e.g., when a new speaker speaks), detecting a change in the sound source, detecting a particular audio source (e.g., when a particular speaker speaks), detecting a period of silence (the length of the silence to be detected as an event may be user-configurable), detecting a change in the direction of the sound source, and the like. For example, according to one technique, events detector 108 may perform sound localization on 4-channel audio in real-time and save a key frame from the captured video stream in the direction of the sound. Further details related to such a technique are described in D. S. Lee, B. Erol, J. Graham, J. J. Hull, and N. Murata, “Portable meeting recorder,” ACM Multimedia, pp. 493-502, 2002, the entire contents of which are herein incorporated by reference for all purposes. Events detector 108 may also detect an event in the audio information each time the sound direction is changed. Events detector 108 may also identify “audio hotspots” from the audio stream such as occurrences of applause, laughter, singing, shouting, etc. A technique for performing such analysis is described in Qian Hu et al, “Audio Hot Spotting and Retrieval Using Multiple Features” HLT-NAACL 2004 Workshop on Interdisciplinary Approaches to Speech Indexing and Retrieval, 2004, the entire contents of which are herein incorporated by reference for all purposes.

In addition to audio information, events detector 108 may also process and detect events from other types of information. Events detector 108 may analyze video information to determine one or more events based upon the contents of the video information. For example, a video stream may be analyzed for “visual hotspots” such as occurrences in the video stream of somebody leaving the room or getting up to the whiteboard to write something, someone making gestures, etc. Examples of techniques for performing such analyses are described in D. S. Lee, B. Erol, J. Graham, J. J. Hull, and N. Murata, “Portable meeting recorder,” ACM Multimedia, pp. 493-502, 2002, and B. Erol, D. Lee, J. Hull, “Multimodal summarization of meeting recordings,” ICME, 2003, the entire contents of which are herein incorporated by reference for all purposes.

As another example, events detector 108 may detect events related to slides (referred to as slide-related events). Slide-related events may be detected from various types of information. For example, slide-related events may be detected from a video stream captured from a computer executing a slides presentation such as a PowerPoint presentation. Slide-related events may also be determined from slides information captured directly from an application used for the slides presentation (e.g., from a MS PowerPoint application). Slide-related events may also be determined from video information captured by a camera that may be pointed to a screen on which the slides are shown and configured to capture a video of the slides presentation. Events detector 108 may also detect slide-related events from analyzing other types of captured information. Slide-related events may comprise, but are not restricted to, determining a slide change event (e.g., when a new slide is shown), consecutive slide changes in a short time, elapsing of a user-configurable time period without a change in slide, no slide-related event for a period of time, etc. In one embodiment, slide-related events may be detected by extracting keyframes from captured video information.

Further examples of different events and techniques that may be used by events detector 108 are described in D. S. Lee, B. Erol, J. Graham, J. J. Hull, and N. Murata, “Portable meeting recorder,” ACM Multimedia, pp. 493-502, 2002, T. Nishimura, H. Yabe, and R. Oka, “Indexing of human motion at meeting room by analyzing time-varying images of omni-directional camera,” Conference on Computer Vision, vol. 1, pp. 1-4, 2000, B. Erol, D. Lee, J. Hull, “Multimodal summarization of meeting recordings,” ICME, 2003, and R. Cutler, Y. Rui, A. Gupta, J. J. Cadiz, and I. Tashev, “Distributed meetings: A meeting capture and broadcasting system,” ACM Multimedia, 2002, the entire contents of which are herein incorporated by reference for all purposes.

In addition to detecting events from the digital information, events detector 108 may also be configured to generate or determine a visual representation for each detected event. The visual representation may be determined from the digital information. The visual representation may be used to display the detected event. Various different techniques may be used to generate a visual representation for an event. For example, the visual representation for an event may be in the form of a text string describing the event, a keyframe or image selected from the digital information (e.g., selected from the video information stream) when the event occurred, or any other representation that is representative of the event. Various types of visual representations may be used.

A user may customize the functioning of events detector 108 to suit the user's needs. For example, a user may configure events detector 108 to detect only those events that are of interest to the user. These events of interest to the user may be a subset of the events that events detector 108 is capable of detecting. A user may also configure events detector 108 to detect user-specified types of events.

Events detector 108 is configured to communicate information related to the detected events to annotating interface 110 for further processing. The information communicated to annotating interface 110 may comprise information identifying the detected events and visual representations associated with the events. Annotating interface 110 is configured to display the detected events to a user 114. The events may be displayed by displaying the visual representations associated with the detected events. The events may be displayed in chronological order based upon the time of occurrence of the events in the digital information. For example, in one embodiment, the events may be displayed along a timeline. Additional information may also be displayed for each event such as the time in the recorded information when the event occurs, the type of recorded information from which the event was detected, the technique used for detecting the event, and the like. An example of a graphical user interface (GUI) that may be used to display detected events is depicted in FIG. 5 and described below.

Annotating interface 110 enables a user to annotate the digital information based upon events determined from the digital information. Annotating interface 110 is configured to display to the user one or more events detected by events detector 108 from the digital information that is to be annotated. A user may then add annotations by selecting one or more of the displayed events. The selected events represent events for which annotations are to be added to the digital information. Portions of the digital information that are to be annotated are determined from the user-selected events.

Various different ways may be provided for selecting events. In one embodiment, annotating interface 110 is a graphical user interface that displays the detected events and provides options for the user to select one or more of the displayed events. The user may use an input device such as a mouse to select one or more events from the displayed events for which the user wishes to add annotations to the digital information.

The annotations may be added to the digital information by annotating interface 110 or by some other component. For example, in the embodiment depicted in FIG. 1, annotations may be added by annotating interface 110 or by server 104. For example, in server 104 is configured to perform the annotations, after one or more events have been selected by the user, annotating interface 110 may communicate information identifying the selected events to server 104. Other information related to the user-selected events such as information related to the user that made the selections, etc., may also be communicated to server 104. Server 104 may then be configured to annotate the captured digital information (e.g., the digital information stored in database 106) based upon the user-selected events.

The digital information may be annotated in different ways. In one embodiment, for a user-selected event, a time when the event occurs in the digital information is determined and that time is used to determine where to annotate the digital information. For example, an annotation may be added to the digital information at the time when the event occurs in the digital information. Alternatively, the digital information may be annotated at the start of the selected event (i.e., at the start time of the selected event), at the end of the event (i.e., at the end time of the selected event), middle of the event, or any point during the selected event, etc. Various other methods (e.g., time of event plus 2 minutes, time or event minus 5 minutes, etc.) based upon the time associated with the event may be used to determine where the annotation is to be added. Alternatively, the digital information may be annotated for the entire duration of the selected event (e.g., from the start time of the event to the end time of the event). The manner in which the digital information is to be annotated may be specified or configured by the user of the system. In one embodiment, in the default mode, the digital information is annotated at the start time of each selected event.

Annotations 116 may be stored as part of digital information in database 106. For example, if information for a particular record 112 is annotated, then the annotation information may be stored are as part of the record. The annotation information may also be stored separately and correlated to the digital information which may be stored in a record 112 in database 106.

The contents of each annotation may also vary. In one embodiment, an annotation may comprise only a timestamp. The timestamp may correspond to the time when an event, for which the annotation is being added, occurs in the digital information. In other embodiments, other information may also be stored as part of an annotation such as time and date when the annotation was applied, information related to the user who selected the event that caused the annotation (e.g., the user who caused the annotation to be applied), location of the user when the annotation was applied (e.g., a user may be in his/her office when the annotation was applied to the recorded information of a meeting that occurred three weeks ago in another building), mood of the user (e.g., the heart rate of the user obtained from a heart monitor worn by the user), environmental conditions when the user selected the event that resulted in the annotation (e.g., surrounding temperature), the type of event, and the like.

In the manner described above, events detector 108 and annotating interface 110 facilitate the annotation process. Events detector 108 is configured to detect events from the digital information to be annotated. Annotating interface 110 is configured to display the detected events to a user, receive information from the user identifying user-selected events, and annotate (or cause the annotation) the digital information based upon the user-selected events. In this manner, embodiments of the present invention provide a simple, convenient, and efficient technique for performing events-driven annotations.

Annotating interface 110 may also be used to select the digital information to be annotated. A list of available records storing digital information may be displayed to the user and the user may be allowed to select a record for which annotations are to be added. For example, database 106 may store several records 112, each record storing information captured during a recording session. For example, multiple meeting records may be stored for information captured during multiple meetings. The user may then select a meeting record to be annotated. Information from the selected record may be played back to the user and also streamed to events detector 108 for events detection. Events detected by events detector 108 may be displayed by annotating interface 110. A user may then select one or more of the displayed events. The information in the selected record may then be annotated based upon the user-selected events. The annotations may subsequently be used to search, browse, or perform other operations on the annotated information.

As previously described, the information that is annotated may be captured during a recording session. For example, a recording session at a meeting may be used to capture information during the meeting. The recording session may last the length of the meeting or for a shorter time (e.g., only the first half of the meeting may be recorded). The annotation-related processing including the operations of detecting events, displaying the detected events, receiving user-selections of events, and the subsequent annotation of the information may be performed during the recording session and/or at some time after the recording session. The annotations are then available to be used for functions such as searching and browsing the digital information. In an embodiment where the annotation operations are performed during recording session, the annotated information can be searched and/or browse during the recording session. For example, information may be captured during a meeting (i.e., a recording session during a meeting). As information is captured during the meeting, the captured information may undergo events detection. Displaying of the detected events, receiving of user selection of events, and annotating the information may be performed while the recording session is continuing during the meeting. The annotation may then be used for searching and browsing during the recording session and during the meeting.

Events detector 108 and annotating interface 110 may be implemented in software (e.g., code or instructions executed by a processor), in hardware, or combinations thereof. Communication between the various components depicted in FIG. 1 may be implemented using various communication protocols and methods such as various messaging protocols, socket calls, and the like. Various different types of communication links may be used to facilitate the communications including hardwire links, optical links, satellite or other wireless communications links, wave propagation links, or any other mechanisms for communication of information.

FIG. 2 depicts a simplified high-level flowchart 200 for annotating information according to an embodiment of the present invention. The processing depicted in FIG. 2 may be performed by software (code modules or instructions) executed by a processor, hardware modules, or combinations thereof. Flowchart 200 depicted in FIG. 2 is merely illustrative of an embodiment of the present invention and is not intended to limit the scope of the present invention. Other variations, modifications, and alternatives are also within the scope of the present invention. The method depicted in FIG. 2 may be adapted to work with different implementation constraints.

As depicted in FIG. 2, the processing is initiated upon accessing or receiving the digital information to be annotated (step 202). For example, the information captured during a meeting using one or more capture devices may be received in 202. The user may also select information to be annotated and that information may be accessed in 202. The digital information to be annotated information may comprise information of one or more types.

The digital information accessed or received in 202 is processed to identify a set of one or more events from the digital information (step 204). As described above, various events may be detected and various techniques may be used to detect the events. In one embodiment, a user may configure which events are to be detected.

The set of events detected in 204 is then output to the user (step 206). In one embodiment, a graphical user interface may be provided that displays the detected events. A user then may select one or more events from the displayed events for which annotations are to be added. Information is received indicative of one or more events selected by the user from the events output in 206 (step 208).

The digital information is then annotated based upon the one or more events selected by the user in 208 (step 210). As previously stated, for a selected event, the digital information may be annotated based upon a time associated with selected event, such as the time when the event occurs in the digital information, the starting point of the event, the end of the event, middle of the event, or some other time based upon the event, etc. The information may also be annotated for the entire duration of the selected event.

The annotations may be used for various operations on the information such as searching and browsing the information (step 212).

The processing depicted in FIG. 2 may be performed in an iterative manner. As new information is captured by the capture devices, the new information may be processed to detect events, and the captured information may be annotated based upon user-selected events.

In the manner described above, a user is able to annotate digital information by selecting events for which annotations are to be added. The events-based annotation technique provides great flexibility to the user to add annotations to the digital information in a simple and easy manner. The processing may be performed in real time during the recording session or at some time subsequent to the recording session during which the digital information that is annotated is captured.

In the embodiment described above, annotating interface 110 provides an interface via which a user selects events for which annotations are to be added to the digital information. As described above, annotating interface 110 outputs the detected events to a user and also enables a user to select one or more of the displayed events. Annotating interface 110 may take various other forms in alternative embodiments. One such alternative embodiment is depicted in FIG. 3.

FIG. 3 depicts another simplified system 300 that may incorporate an annotation system according to an embodiment of the present invention. As depicted in FIG. 3, system 300 comprises one or more capture devices 102, a server 104, a database 106, an events detector 108, an annotating interface 110, and a snap-to-event manager 302. FIG. 3 is merely illustrative of an embodiment incorporating the present invention and does not limit the scope of the invention as recited in the claims. One of ordinary skill in the art would recognize other variations, modifications, and alternatives.

Capture devices 102, server 104, events detector 108, and database 106 are the same as those depicted in FIG. 1. Annotating interface 110 may take various different forms. Annotating interface 110 provides an interface for the user to indicate when the digital information is to be annotated. In one embodiment, annotating interface 110 may be a device that a user may use to indicate when an annotation is to be added to the digital information. For example, annotating interface 110 may be a one-button input device. During a meeting, while information is being recorded for the meeting (i.e., during a recording session for the meeting), a user may click the button of the device whenever the captured information is to be annotated. When the user clicks the button, a signal is communicated from the device to snap-to-event manager 302. In one embodiment, the signal may comprise information identifying the time when the user clicked the button. In certain embodiments, instead of the present time, upon selecting the button, a signal identifying the present time plus or minus a user configurable delta (e.g., present time minus 30 seconds, present time minus 2 minutes, present time plus 1 minute, etc.) may be communicated to snap-to-event manager 302. The signal may be communicated to snap-to-event manager 302 using wired or wireless communications (e.g., if the device is a RF device). As described below, the information captured during the meeting is annotated responsive to the signal.

Annotating interface 110 may also take other forms. In general, annotating interface 110 may be any interface that enables a signal to be sent to snap-to-event manager 302 indicating when an annotation is to be added to the digital information. Various different user actions or other triggers may trigger the signal. Examples of user actions that may trigger the signal include clapping hands, uttering specific words or phrases, making certain gestures, using a device, etc. In some embodiments, the signal sent to snap-to-event manager 302 may comprises information such as the time when the signal was triggered, information related to the user that caused the signal to be triggered, and other like information.

Snap-to-event manager 302 receives an input signal from annotating interface 110 and information identifying events detected by events detector 108. According to an embodiment of the present invention, snap-to-event manager 302 is configured to determine an event from events detected by events detector 108 whose start time is closest in time (as compared to start times of other events detected from the digital information) and occurs prior to the time associated with the signal received from annotating interface 110 (i.e., the last detected event prior to the time associated with the signal). The time associated with the signal may be determined from information included in the signal. In other embodiments, snap-to-event manager 302 may be configured to determine the time associated with the signal (e.g., the time when snap-to-event manager 302 received the signal) and determine a closest event based upon that time. Snap-to-event manager 302 thus translates the signal received from annotating interface 110 to an event detected by events detector 108 that occurs closest in time and prior to the signal.

In an embodiment where server 104 is configured to add the annotations, snap-to-event manager 302 communicates information related to the event determined for the signal to server 104. The information communicated to server 104 may include information identifying the time of occurrence of the event determined for the signal. The information communicated to server 104 may also include other information such as information identifying the event determined by snap-to-event manager 302 for the signal, information related to the user whose action caused the signal to be sent to snap-to-event manager 302, and other information.

In certain embodiments, the user can indicate the types of events that are of interest to the user and that the user would like to annotate. In these embodiments, snap-to-event manager 302 is configured to select an event from the events detected by events detector 108 that is of the user-specified type and occurs prior to and closest to the time associated with the signal received from annotating interface 110. For example, the user may be interested only in events indicating when a new slide is shown. In this example, snap-to-event manager 302 is configured to determine an event indicative of a new slide being shown that occurs closest in time to and prior to the time associated with the signal received from annotating interface 110. In this scenario, the event determined for the signal may not be the closest prior event to the signal time as there may be another event of a different type that occurred after the selected event but prior to the signal time. Snap-to-event manager 302 communicates information related to the event determined for the signal to server 104.

Based upon the event information received from snap-to-event manager 302, server 104 annotates the digital information based upon the event determined for the signal. As described above, the information may be annotated in different ways. For example, the recorded information may be annotated at the start of the selected event (i.e., at the start time of the selected event), at the end of the event (i.e., at the end time of the selected event), middle of the event, some other time based upon the event, etc. Alternatively, the digital information may be annotated for the entire duration of the selected event. The manner in which the digital information is annotated may be specified or configured by the user of the system. In one embodiment, in the default mode, the digital information is annotated at the start time of the selected event.

The annotation may be stored as part of the digital information, for example as part of record 112 or may be stored separately and correlated to the digital information. As described above, the annotation may store various different types of information such as time information, and other information. In the embodiment described above, server 104 is responsible for annotating the digital information. In alternative embodiments, the annotations may also be added by other components. For example, snap-to-event manager 302 may be configured to annotate the digital information in alternative embodiments.

The annotation-related operations including functions performed by snap-to-event manager 302 may be performed during a recording session when the information is being captured or some time after the recording session. When performed during the recording session, the annotated information may be available for browsing and searching (or other operations) during the recording session. For example, a user may be able to browse and search information captured during the meeting while the meeting is proceeding.

Annotating interface 110 and snap-to-event manager 302 may be implemented in software (e.g., code or instructions executed by a processor), in hardware, or combinations thereof. Communication between the various components depicted in FIG. 3 may be implemented using various communication protocols and methods such as various messaging protocols, socket calls, and the like. Various different types of communication links may be used to facilitate the communications including hardwire links, optical links, satellite or other wireless communications links, wave propagation links, or any other mechanisms for communication of information.

FIG. 4 depicts a simplified high-level flowchart 400 for annotating information according to an embodiment of the present invention. The processing depicted in FIG. 4 may be performed by software (code modules or instructions) executed by a processor, hardware modules, or combinations thereof. Flowchart 400 depicted in FIG. 4 is merely illustrative of an embodiment of the present invention and is not intended to limit the scope of the present invention. Other variations, modifications, and alternatives are also within the scope of the present invention. The method depicted in FIG. 4 may be adapted to work with different implementation constraints.

As depicted in FIG. 4, processing is initiated upon receiving or accessing the information to be annotated (step 402). The information may be received during a recording session, for example, information may be captured and received during a recording session during a meeting. One or more capture devices may be used to capture the information. The digital information received in 402 may comprise information of one or more types.

The digital information received in 402 is analyzed to identify a set of one or more events from the information (step 404). As described above, various events may be detected and various techniques may be used to detect the events. In one embodiment, a user may configure the events to be detected.

A signal may be received from the annotating interface (step 406). As previously described, the signal may be received due to some user action indicating that the user wishes to annotate the recorded information when the action is performed. For example, a user may click a button to indicate that the captured information is to be annotated. In one embodiment, the signal may be received during a recording session while information is being captured. The signal may also be received during playback of previously recorded information that is to be annotated.

An event is then determined from the set of events detected in 404 for the signal received in 406 (step 408). In one embodiment, as part of 408, a time associated with the signal is determined and an event selected from the set of events detected in 404 based upon the time. In one embodiment, the selected event is one whose start time is closest to (as compared to start times of other events detected in the recorded information) the time associated with the signal and occurs prior to the time associated with the signal.

The digital information is then annotated based upon the event determined in 408 selected (step 410). As part of 410, a time associated with the event determined in 408 may be determined and used to annotate the information. For example, an annotation may be added to the digital information at the time when the event occurs in the digital information, at the start of the selected event, at the end of the event, middle of the event, or any point during the selected event, etc. Various other methods (e.g., time of event plus 2 minutes, time or event minus 5 minutes, etc.) based upon the time associated with the event may be used to determine where the annotation is to be added. Alternatively, the digital information may be annotated for the entire duration of the selected event.

The annotations may then be used for performing various operations on the digital information such as searching and browsing the information (step 412).

The steps depicted in FIG. 4 may be performed during the meeting. The processing depicted in FIG. 4 may be performed in an iterative manner. As new information is captured by the capture devices, the new information may be processed to detect events, and the recorded information may be annotated based upon user-selected events.

In the manner described above, various different interfaces may be provided that enable a user to annotate information that may be captured during a recording session. Signals or selections received from the user are translated to events detected in the captured digital information and the digital information is annotated based upon the detected events. The events-based annotation technique provides great flexibility to the user to add annotations to the digital information in a simple and easy manner. The processing may be performed in real time during the meeting.

FIGS. 5A and 5B depict a simplified user interface 500 for displaying events detected in the digital information to the user and for enabling a user to select one or more of the detected events according to an embodiment of the present invention. As depicted in FIG. 5A, graphical user interface 500 displays a timeline 502 that is divided into segments. The segments on FIGS. 5A and 5B are of 15 seconds duration. A visual representation 504 is displayed for each detected event. The visual representation for an event is displayed in the segment of the timeline when the event occurs. A user-selectable box 506 is displayed for each segment. A user can select an event displayed in a segment by selecting box 506 of that segment. The current time 508 is also displayed. A user causes annotations to be added for the selected events by selecting “Bookmark Now” button 508. Timeline 502 scrolls in a horizontal direction from right to left with the passage of time. This is evident from FIG. 5B wherein timeline 502 has moved by one time segment and the new current time is displayed. In this manner, as new information is received and processed, for example during a recording session, the events detected in the information are displayed.

FIG. 6 is a simplified block diagram of a computer system 600 that may be used to practice an embodiment of the present invention. As shown in FIG. 6, computer system 600 includes a processor 602 that communicates with a number of peripheral devices via a bus subsystem 604. These peripheral devices may include a storage subsystem 606, comprising a memory subsystem 608 and a file storage subsystem 610, user interface input devices 612, user interface output devices 614, and a network interface subsystem 616.

Bus subsystem 604 provides a mechanism for letting the various components and subsystems of computer system 600 communicate with each other as intended. Although bus subsystem 604 is shown schematically as a single bus, alternative embodiments of the bus subsystem may utilize multiple busses.

Network interface subsystem 616 provides an interface to other computer systems, networks, and devices. Network interface subsystem 616 serves as an interface for receiving data from and transmitting data to other systems from computer system 600.

User interface input devices 612 may include a keyboard, pointing devices such as a mouse, trackball, touchpad, or graphics tablet, a scanner, a barcode scanner, a touchscreen incorporated into the display, audio input devices such as voice recognition systems, microphones, and other types of input devices. In general, use of the term “input device” is intended to include all possible types of devices and mechanisms for inputting information to computer system 600. A user may use an input device to select one or more events from the events displayed to the user in the system depicted in FIG. 1. A user may also use an input device to cause generation of the signal in the system depicted in FIG. 3.

User interface output devices 614 may include a display subsystem, a printer, a fax machine, or non-visual displays such as audio output devices, etc. The display subsystem may be a cathode ray tube (CRT), a flat-panel device such as a liquid crystal display (LCD), or a projection device. In general, use of the term “output device” is intended to include all possible types of devices and mechanisms for outputting information from computer system 600. The detected events may be displayed to the user using an output device in the system depicted in FIG. 1.

Storage subsystem 606 may be configured to store the basic programming and data constructs that provide the functionality of the present invention. Software (code modules or instructions) that provides the functionality of the present invention may be stored in storage subsystem 606. These software modules or instructions may be executed by processor(s) 602. Storage subsystem 606 may also provide a repository for storing data used in accordance with the present invention. Storage subsystem 606 may comprise memory subsystem 608 and file/disk storage subsystem 610.

Memory subsystem 608 may include a number of memories including a main random access memory (RAM) 618 for storage of instructions and data during program execution and a read only memory (ROM) 620 in which fixed instructions are stored. File storage subsystem 610 provides persistent (non-volatile) storage for program and data files, and may include a hard disk drive, a floppy disk drive along with associated removable media, a Compact Disk Read Only Memory (CD-ROM) drive, an optical drive, removable media cartridges, and other like storage media.

Computer system 600 can be of various types including a personal computer, a portable computer, a workstation, a network computer, a mainframe, a kiosk, or any other data processing system. Due to the ever-changing nature of computers and networks, the description of computer system 600 depicted in FIG. 6 is intended only as a specific example for purposes of illustrating the preferred embodiment of the computer system. Many other configurations having more or fewer components than the system depicted in FIG. 6 are possible.

Although specific embodiments of the invention have been described, various modifications, alterations, alternative constructions, and equivalents are also encompassed within the scope of the invention. The described invention is not restricted to operation within certain specific data processing environments, but is free to operate within a plurality of data processing environments. Additionally, although the present invention has been described using a particular series of transactions and steps, it should be apparent to those skilled in the art that the scope of the present invention is not limited to the described series of transactions and steps.

Further, while the present invention has been described using a particular combination of hardware and software, it should be recognized that other combinations of hardware and software are also within the scope of the present invention. The present invention may be implemented only in hardware, or only in software, or using combinations thereof.

The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that additions, subtractions, deletions, and other modifications and changes may be made thereunto without departing from the broader spirit and scope of the invention as set forth in the claims. 

1. A method performed by a computer system of annotating digital information, the method comprising: identifying a set of one or more events from the digital information; outputting, via an output device, information identifying the set of events; receiving user input indicating selection of at least one event from the set of events; and annotating the digital information based upon the at least one event.
 2. The method of claim 1 wherein annotating the digital information comprises: determining a time associated with the at least one event; and annotating the digital information based upon the time associated with the at least one event.
 3. The method of claim 1 wherein annotating the digital information comprises: annotating the digital information for a duration of the at least one event.
 4. The method of claim 1 further comprising determining a visual representation for each event in the set of events, and wherein outputting the information identifying the set of events comprises outputting the visual representation for each event in the set of events.
 5. The method of claim 1 wherein: the digital information is captured during a recording session; and the identifying the set of events, outputting information identifying the set of events, receiving the user input, and annotating the digital information are performed during the recording session.
 6. The method of claim 1 wherein: the digital information comprises audio information and video information; and identifying the set of one or more events comprises analyzing the audio information and the video information to identify the set of events.
 7. A method performed by a computer system of annotating digital information, the method comprising: identifying a set of one or more events from the digital information; receiving a signal; determining a first event for the signal from the set of events; and annotating the digital information based upon the first event.
 8. The method of claim 7 wherein the signal is caused due to an action performed by a user.
 9. The method of claim 7 wherein the digital information is captured during a recording session and wherein the signal is caused by an action performed by a user during the recording session.
 10. The method of claim 7 wherein determining the first event from the set of events for the signal comprises: determining a time associated with the signal; and determining an event from the set of events whose start time is prior to and closest to the time associated with the signal.
 11. The method of claim 7 wherein annotating the digital information comprises: determining a time associated with the first event; and annotating the digital information based upon the time associated with the first event.
 12. The method of claim 7 wherein annotating the digital information comprises: annotating the digital information for a duration of the first event.
 13. The method of claim 7 wherein: the digital information is captured during a recording session; and the identifying the set of events, receiving the signal, determining the first event, and annotating the digital information are performed during the recording session.
 14. A system for annotating digital information, the system comprising: a memory storing the digital information; an output device; and a processor couple to the memory, the processor configured to: identify a set of one or more events from the digital information; cause the output device to output information identifying the set of events; receive user input indicating selection of at least one event from the set of events; and annotating the digital information based upon the at least one event.
 15. The system of claim 14 wherein the processor is configured to: determine a time associated with the at least one event; and annotate the digital information based upon the time associated with the at least one event.
 16. The system of claim 14 wherein the processor is configured to annotate the digital information for a duration of the at least one event.
 17. The system of claim 14 comprising: a set of one or more capture devices configured to capture the digital information during a recording session; and wherein the processor is to configured to identify the set of one or more events, cause the output device to output the information identifying the set of events, receive user input, and annotate the digital information during the recording session.
 18. A system for annotating digital information, the system comprising: a memory storing the digital information; and a processor couple to the memory, the processor configured to: identify a set of one or more events from the digital information; receive a signal; determine a first event for the signal from the set of events; and annotate the digital information based upon the first event.
 19. The system of claim 18 wherein the signal is caused due to an action performed by a user.
 20. The system of claim 18 wherein the digital information is captured during a recording session and wherein the signal is caused by an action performed by a user during the recording session.
 21. The system of claim 18 wherein the processor is configured to: determine a time associated with the signal; and determine an event from the set of events whose start time is prior to and closest to the time associated with the signal.
 22. The system of claim 18 wherein the processor is configure to: determine a time associated with the first event; and annotate the digital information based upon the time associated with the first event.
 23. The system of claim 18 wherein the processor is configured to annotate the digital information for a duration of the first event.
 24. The system of claim 18 comprising: a set of one or more capture devices configured to capture the digital information during a recording session; and wherein the processor is configured to identify the set of events, receive the signal, determine the first event, and annotate the digital information during the recording session.
 25. A computer-readable medium storing a plurality of instructions for controlling a data processor to annotate digital information, the plurality of instructions comprising: instructions that cause the data processor to identify a set of one or more events from the digital information; instructions that cause the data processor to output, via an output device, information identifying the set of events; instructions that cause the data processor to receive user input indicating selection of at least one event from the set of events; and instructions that cause the data processor to annotate the digital information based upon the at least one event.
 26. The computer-readable medium of claim 25 wherein the instructions that cause the data processor to annotate the digital information comprise: instructions that cause the data processor to determine a time associated with the at least one event; and instructions that cause the data processor to annotate the digital information based upon the time associated with the at least one event.
 27. The computer-readable medium of claim 25 wherein the instructions that cause the data processor to annotate the digital information comprise: instructions that cause the data processor to annotate the digital information for a duration of the at least one event.
 28. The computer-readable medium of claim 25 wherein: the digital information is captured during a recording session; and the plurality of instructions comprises instructions that cause the data processor to identify the set of events, output information identifying the set of events, receive the user input, and annotate the digital information during the recording session.
 29. A computer-readable medium storing a plurality of instructions for controlling a data processor to annotate digital information, the plurality of instructions comprising: instructions that cause the data processor to identify a set of one or more events from the digital information; instructions that cause the data processor to determine a first event from the from the set of events for a signal; and instructions that cause the data processor to annotate the digital information based upon the first event.
 30. The computer-readable medium of claim 29 wherein the signal is caused due to an action performed by a user.
 31. The computer-readable medium of claim 29 wherein the instructions that cause the data processor to determine the first event from the set of events for the signal comprise: instructions that cause the data processor to determine a time associated with the signal; and instructions that cause the data processor to determine an event from the set of events whose start time is prior to and closest to the time associated with the signal.
 32. The computer-readable medium of claim 29 wherein the instructions that cause the data processor to annotate the digital information comprise: instructions that cause the data processor to determine a time associated with the first event; and instructions that cause the data processor to annotate the digital information based upon the time associated with the first event.
 33. The computer-readable medium of claim 29 wherein the instructions that cause the data processor to annotating the digital information comprise: instructions that cause the data processor to annotate the digital information for a duration of the first event.
 34. The computer-readable medium of claim 29 wherein: the digital information is captured during a recording session; and the plurality of instructions comprises instructions that cause the data processor to identify the set of events, determining the first event, and annotate the digital information during the recording session. 